The cornerstone of collaborative development
Git is a software version control system that enables distributed collaboration of engineers working all over the world. It allows for …
Overview
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Reviewer Pros & Cons
Pricing
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
5 people also want pricing
Alternatives Pricing
What is GitHub?
GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans…
What is Liquibase?
Liquibase is a database change management tool that helps teams release software faster and safer by bringing the database change process into existing CI/CD automation. According to the 2021 Accelerate State of DevOps Report, elite performers are 3.4 times more likely to incorporate database…
Product Demos
Git Merge and Rebase Demo
YouTube
Git hooks, practical uses (yes, even on Windows)
YouTube
Git Tutorial For Beginners | What is Git and GitHub? | Git Tutorial | DevOps Tutorial | Simplilearn
YouTube
Git Push Command | Git Bash Tutorial | Git Commands | Git Tutorial For Beginners | Simplilearn
YouTube
Product Details
- About
- Tech Details
What is Git?
Git Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(74)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Recommendations
Git is a widely used version control system that offers a range of use cases for different teams and organizations. Engineering and dev-ops teams rely on Git to handle version control of codebases, allowing them to create branches for features and bug fixes. By using Git, they can easily merge and release code to different environments, ensuring smooth software development processes.
Freelance software developers also find value in Git as it enables them to work on multiple machines and platforms, providing flexibility and backup of source code. They appreciate the ability to easily manage and track changes in their codebase, ensuring effective collaboration with clients and the ability to revert back if needed.
Organizations benefit from Git's ability to store source code across multiple repositories and branches. They typically have a mainline development branch for code review and automated builds, allowing for efficient management of projects. Git addresses the problem of multiple people updating a codebase by managing merging of changes, storing committed changes in a log for review, and offering rollback options when necessary.
Furthermore, Git fosters collaboration and code contribution among developers by preventing conflicts and facilitating efficient software development. It is successfully utilized by various departments like Tech Writing and Implementation, helping streamline release cycles and integrating smoothly with other tools like Bitbucket for pull requests.
Additionally, Git is an essential tool for managing app development processes. Its usage ensures faster release of changes while minimizing negative impacts on existing functionalities. Many companies rely on Git to manage massive codebases and enable cross-team code review, making it a reliable solution for tracking project progress and ensuring software security vulnerabilities are addressed.
Overall, Git's ease of use and cleaner approach to version control have received praise from users. It is widely recognized as stable and reliable for managing code, providing a centralized area for sharing and collaborating on projects across different teams.
In summary, whether it's handling version control, managing projects for customers, tracking changes in websites or internal scripting projects, or enabling concurrent work, Git proves to be a valuable and versatile tool for developers, freelancers, and organizations alike.
Users commonly recommend learning Git thoroughly to utilize its benefits for code repository management, version control, and team collaboration. They emphasize the importance of utilizing the command line interface and following established processes for branching and merging. Users also encourage exploring advanced features, seeking support from online resources like Stackoverflow, and considering other alternatives if needed. Overall, users consider Git to be an essential tool with excellent features and community support in the software development realm.
Attribute Ratings
Reviews
(1-22 of 22)Companies can't remove reviews or game the system. Here's why
June 28, 2021
Git has everything you need for code
Git is used across the organization for version control of the code build. It helps us track our deployments and snapshots of various artifacts we develop. All kinds of programming languages and files are checked in to git via github. We also control the code migration between various environments using Git.
- Pull requests to control what's checked in where
- 2-step commit and push to enable cleaner check-in process
- Personal forks to help developers with quick development and testing
- I feel that code merging using command line is not very straightforward when there are conflicts
January 18, 2020
Every developer should be using Git
We use Git as source control for all our projects across our entire department. I know there are other departments in our organization that use it as well. I also use Git for all my personal projects and side projects. Git enables all of our developers to collaborate and contribute code to our projects simultaneously, preventing conflicts.
- Source control
- Collaboration
- Difficult for people who aren't used to the command line (but there are apps for that).
- Some specific situations where it's difficult to figure out the right way to do things.
January 18, 2020
Easy to use and collaborate
Git is used mostly as a source version controlling system which allows developers to collaborate with one another. It helps teams to contribute to various projects by pushing code to GIT. It can be used for release versioning. It is helpful to know which version has been released in production and at what codebase.
- Flexibility
- Version history
- Merge conflict
- Amending commits in remote repo
November 23, 2019
Mandatory tool for Software Development
Our whole company uses Git for code collaboration where a team can continuously develop features for the software. Also, it allows our peers to review the code and once necessary approvals are received, we can merge the code ensuring proper workflow is followed. Git gives us helpful insight regarding project progress, software security vulnerabilities.
- It's a great version control system helps us to develop the software incrementally releasing stable versions.
- Git gives proper reminders when ever the my peers requests code review approval.
- Git can be easily integrated with other software like Slack, Developer workbenches like Web Storm, Visual Studio Code, etc.
- Git commands are very intuitive, makes us to easily understand and get the work done.
- Git gives us great insights on the project progress like the number of Pull Requests Raised, Closed Issues, etc.
- Git gives an intuitive UI, so the user can operate through the web.
- Git can still improve UI design.
- Git can also embed some artificial intelligence, and suggest alternate ways to solve the problem when the code review happens.
- Git can also suggest when the deadline for any reviews should be closed so it helps the developers in the team to finish that PR within time.
October 05, 2019
GIT - Version Manager for Fast delivering Teams
GIT is being used as a version control tool within our organization. Its been used to speed up the code deliveries to different environment and track the changes being deployed to the software product.
GIT being widely used tool has proven itself to be more stable and reliable for code management within organizations and vital for organizations who share their codes(Ex : Integration kits) with their customers IT teams.
GIT being widely used tool has proven itself to be more stable and reliable for code management within organizations and vital for organizations who share their codes(Ex : Integration kits) with their customers IT teams.
- Better tool for products having faster release cycles.
- Feature branching is a vital feature available in GIT as it make sure that not all code is merged to the master branch unless its production ready.
- Easy to use commands and speed in Git operations.
- GIT Commands could be more natural and intuitive.
- GIT should improve handling of files like exe, image, docs etc.
- Code commits on multiple branches should be available.
September 28, 2019
Don't lose a line of work, Git it backed up.
Git is used across most of the organization, if not all of it. Git is a Version Control System, which means that allows you to "backup" and control who edited your files, providing its best value when it comes to plain text files, such as code.
- Git is a distributed system. Usually adding the word "distributed" makes things very complex and messy, but not with Git, thanks to its branches and merge control.
- It's insanely fast.
- Merges sometimes will produce conflicts that are time-consuming but its resolution is trivial if you consider the history of changes.
February 12, 2019
Git things done
In our organization, Git is used by several departments for file versioning, collaborative work on the same source code, change tracking, branch merging, version comparison etc. Especially because we have distributed teams all over the world, we needed a reliable tool to achieve these goals, and Git was the natural choice.
- File versioning - easy to see the history of the changes.
- Collaborative work on the same source code -- by providing the ability to create branches.
- Merging branches and comparing versions made easy.
- It is free and open source.
- Git is so popular that when hiring, it is easy to find developers who already know this.
- To use Git at its full capabilities, one needs to spend some time learning it.
- Command line usage may be an issue to developers used more with GUIs. For those, you may need to add a free GUI or purchase something like Bitbucket.
- Merging code when there are conflicts can be difficult sometimes from the command line.
- Git may have bundled in more features that it needs. Most people just need the basics: pull, edit, push, merge.
February 04, 2019
Git: a solid version control tool
Git is our core version control tool in my company and it is used not only in our development department but in multiple other departments like Tech Writing and Implementation. In development, we use Git to track our development changes and to organize our release cycles with different branches to track our stages. We utilize tools that integrate with Git like Bitbucket to have a front end UI that helps us manage things like pull requests, which are branches off of QA for development changes we would like to add to release. Git is the core infrastructure in what we do here and I have been using it every day for the past 6 years.
- Ability to create branches off current releases to modify code that can be tested in a separate environment.
- Each developer had their own local copy of branches so it minimizes mistakes being made.
- Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
- Conflicts are displayed nicely so that developers can resolve with ease.
- Sometimes conflicts arise over white space which can be annoying.
- You cannot do any advanced features in the built-in GUI, you have to use an application like Bitbucket for these things.
- It can have a very high learning curve for new users because there are so many commands and things you can do that it gets very complex very fast.
January 16, 2019
Git - Best Source Control Management Tool
My organization uses Git for version control of our various codebases. It is used by the engineering and dev-ops teams. We use git because it reliably handles creating branches for various features and bug fixes, and provides an effective and trusted way to merge and release that code to our different environments.
- Ability to create branches and merge those changes in - very cleanly and in an organized way. Other features such as cherry-picking and rolling back are extremely useful.
- Diff-ing changes is a great utility for reviewing code and understanding the history of code changes.
- Git makes working in teams on the same set of code very possible, compared to some of the alternatives like SVN.
- There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master.
- Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this.
- Many different GUIs, many people (including myself) opt to just use the command-line.
December 17, 2018
Git: Version control for the future
We use Git to manage a truly massive code base. Every developer is added to our enterprise GitHub server and is expected to use it when writing and reviewing code. The problems we try to address with Git include version control and cross team review.
- Code management. This allows us as a team to manage unique code bases for each employee with little to no overhead.
- Code backup and versioning. Git truly has the most rebust and reliable code versioning system in the industry.
- Handling large amounts of unique data from a variety of teams. We sometimes have to work across teams and across organizations when writing and testing code; Git allows us to do this even when developers are on the other side of the world.
- There is a serious lack of GUI clients for Git.
- The command line version of Git is often obtuse and confusing to use.
- When something goes wrong in Git, it often does so spectacularly. We spend a lot of man hours cleaning up Git-created messes.
December 14, 2018
Versioning and branching at their best
We use Git across all of our development projects in order to work on multiple aspects at once and then merge branches as needed. There are four scrum teams and one Kanban team that handles hardware issues. All the scrum teams are developing and maintaining software to various degrees across the organization.
- It's the best at version control that I've seen. Rollbacks are a snap.
- Provides local control down the individual developer level, which in turn allows easy management back up the chain of command.
- Cloning is perfect when you need to copy a project to tweak it without messing with the main branch.
- If you're not a developer, it'll take some time to get the hang of it, particularly some aspects of the API.
- Sometimes the parameters are WAY too long.
November 29, 2018
Git With the Program: Superior Codebase Management
Our organization uses Git for code versioning, namely to track and manage changes to the codebase in a way that avoids accidentally writing over another engineer's code, resolves change conflicts, and provides a rollback option in the event of a breaking change. Git has become an important part of the development workflow for most software engineering teams. The problem Git addresses for us is the problem of having multiple people updating a codebase. One developer might change a portion of the code in one area and another might change it somewhere else, and managing the merging of these changes together is the main job of Git. To facilitate this Git stores every committed change in a log, and this log can be reviewed and even used to roll the code back and reject changes further down the pipeline. In our organization, each engineer creates a new branch from the master codebase whenever they are starting a new task in the project, and once they have completed that task and confirmed the code is stable, the code can be merged into the master codebase and eventually included in the production build. Our team has a strict policy of not merging your own code, so the code is reviewed and approved by another engineer whom merges it in after assessing its impact. We use Git across our engineering department only.
- Git manages the merging of changes from different team members and provides for a way to roll back those changes when necessary.
- Git allows for management of multiple branches of a code project and merging them in through a controlled and considered manner.
- Git provides a complete history of all code changes and who made them, making the process of identifying when breaking code came in a much easier one along with identifying the code to roll back to (when needed).
- Git is a powerful tool for change management and avoiding breaking code making its way into production.
- Git has a steep learning curve in that it has traditionally been used through the command-line interface, and has a lengthy set of commands you must learn how to use to work with it efficiently. Fortunately, there are some good GUI-based applications to help you with this, but to really be a Git master you will have to know how to use in from the console.
- At times it can be difficult to determine just what action is appropriate when a mistake has been made in a Git commit. A deep understanding of how Git works can be required to correctly navigate the steps to recover from a bad commit.
- Git could benefit from an overhaul of its command syntax to focus on the subset of Git commands that most developers use all the time.
- Some Git commands have names that can prompt misunderstandings as to what they actually do. A prime example of this is "git blame" which simply tells you whom made a specific change to the code, but sounds like it is going to automatically report someone to their boss for a dressing-down.
September 12, 2018
Git is the king for a reason
Git is being used by our organization on an information technology department level. We use Git as our sole Version Control system for all of our software releases, maintenance & deployment.
- Git is designed to work in a distributed manner, allowing each developer to run a local node that has full control of the project. Through this, the developer is able to merge his work with others on a main 'branch' & work in sync without having to worry about stepping on your other developers toes.
- Because Git has solved the software problem of dependency, users who commit code that needs to be deleted can just roll back to a restore point, saving precious development time & tons of headaches for Information Technology. This is also very helpful when cloning projects or creating new features on the current project.
- Git has a beautiful command line interface that is intuitive, easy to learn & extensible. You can also observe all the changes you have made in your project throughout the development with just a few simple commands. This diverse set of command-line tools is easy for the end user & very powerful.
- There is currently no way to avoid downloading the entire commit history of a repository into the local copy - this can be problematic when cloning projects that have a history of many working submodules & packages.
- Advanced configurations (managing multiple branches, having commands that take 2+ arguments) can sometimes be overwhelming for inexperienced users & there is definitely a learning slope for new developers.
- You have to be precise when you use your git commands. The nature of Git commands are powerful. So powerful that if you don't know what you are doing and accidentally type a wrong command, you can cause irrevocable damage to your repository & others.
June 15, 2018
GIT is a gift!
GIT is used as a server out of the box. It is being used by the whole organization. Dedicated Git server software helps, amongst other features, to add access control, display the contents of a Git repository via the web, and help managing multiple repositories.
- Unlike centralized version control systems, Git branches are cheap and easy to merge. This facilitates the feature branch workflow very user-understandable.
- Many commands with many options, some commands are non-intuitive and need a level of understanding the internals of Git, commands and arguments are inconsistent to some degree
Git manages the source control over all of our web-related codebases. It allows us to be light and flexible with our approach to not only development and coding, but also using a continuous integration workflow that automates processes in the deployment chain. Without Git, life as a developer would be quite painful indeed.
- It handles many of the complicated features of version control for you like merging branches
- It has a diverse ecosystem of tools that utilize its many features
- Documentation for Git and its workflows can be quickly found and understood
- Some of the commands are a little obtuse if you're not using a Git Client
- Since Git is so widely used in the development space, it's easy to believe that growth and innovation might become stale in the area of version control. Competition is sparse these days and I'm curious if this "Standard" is going to keep moving forward somehow.
- It's hard to fault a tool that is so ubiquitous and hardly gets in your way.
April 20, 2018
An excellent tool to keep all the changes updated
Git is only used in our department. All our code is saved and versioned with Atlassian Stash using Git as version control system. There are at least 15+ projects in the development using this VCS.
- Git branches allow you to work with different features at the same time.
- Git makes programming easy and fun. You can share your code with a team peer or an entire community. You can modify the same file because you're working with local changes instead of a centralized repository.
- At first, it's difficult to learn all the concepts, (rebase, merge, forking). They are conceptually difficult aspects to get in at first sight. You can use a graphic UI to handle it more easily.
March 15, 2018
Git - the new Subversion
Git is one of the source code version control tools used at my organization (the other major one being Subversion). We are using Git to store our source code across multiple repositories and branches (features and bugs). We have a mainline development branch which all our new code is eventually pushed to, after being code reviewed by their branch using pull requests. The development branch in our Git repositories are polled for any changes, and builds are automatically run to verify the code.
- Branching
- What I find as the main benefit of Git is the ease that branches can be created in a repository - whether that's for working on new features or to fix bugs. It's as easy as selecting the code you want to branch from and "git checkout -b newBranch". Mainly I use this for branching from our development branch (also known as trunk) and once the code is finished, we merge the branch back into the development branch. Switching branches in Subversion is a little bit more complex, whereas Git is super easy to use.
- Pull Requests
- Pull requests can be created on a repository allowing code to be reviewed before being merged to the main branch. External tools like Bitbucket can be used to integrate into the Git repositories, allowing users to easily review and comment on your pull requests.
- Local Repositories
- When you use Git, you checkout the repository to your machine locally - and any commits that you make only affect your local repository, rather than the "real" repository at a remote location. This allows you to commit often and finalize all of your code before merging onto the latest development branch.
- Understanding
- Git has a little bit more of a learning curve when compared to other source control solutions, e.g. Subversion - but this is due to the more complex features it offers.
- IDE Support
- There aren't as many plugins for Git when compared to other source control solutions. Subversion has better plugins for IDEs and seems to be well supported.
- Git Bash
- Using Git bash, or the GUI that comes with Git can be slightly daunting at first. Tools like SourceTree are a solution to this problem, as they run the underlying Git commands for you.
March 07, 2018
Git gets it.
We currently use Git to track all changes in our multiple websites and landing pages, along with internal scripting projects. Git addresses the issue of keeping track of the code we have created, and maintains security and redundancy between employees. In this way, we can be sure that no one person or one device has all the information we use daily to keep our systems and websites running.
- Git works quite well to keep a record of the code and the changes made on code for our websites and internal scripting.
- Git allows multiple developers to work on a single project with the checkout process.
- Git allows us to track who makes edits, when they were made, and how we can go back and fix any mistakes or bugs.
- Git is FAST!
- Git can be slow to learn, and much of it is done through the command line.
- Git is a single solution for a code repository, so if you are looking for larger scale backup or documentation, it might not be the right fit.
March 01, 2018
The Awesome Git
I am a freelance, full-stack, software developer. Git repositories are used for all my code. I use multiple machines to create software for different platforms - Ubuntu to create websites to run on Heroku, and iOS apps. Git allows me to work on any machine while away from my normal setup. It also keeps all my source code backed-up, and I have the ability to grant access to my client if required.
- Backup. It's the cheapest and easiest backup solution I've found in 20 years of coding. If/when a machine goes down I know I have no issues with losing work.
- Access. I can access my code on any machine, anywhere I need to be. If I find myself with some spare time, and any machine at hand, I can dive in and carry on working.
- Forking. It's very easy to fork new ideas without losing the current development thread.
- I mainly use xCode and SublimeText, both of which provide a number of useful commands to backup my code to git. I'd like to see further integration, perhaps automated.
February 15, 2018
A must have
I use it for all my projects both professionally and personally. Version control is a must have for development and Git has served me well.
- Great CLI
- Great documentation
- Great support community
- There are nuances to some of the commands that new users might trip up on such as fetch vs. pull
January 18, 2018
Git - The best type of version control
We use git across our entire organization. We used to use SVN back in the day, but switching to Git has made our lives so much better. Ease of use is excellent and it's a much cleaner approach to version control.
- Distributed versioning. Being able to have each developer working on their own stuff without stomping on each others' changes is very important.
- Incremental versions are very crucial to proper development.
- It's so much faster than SVN. You can check out a repo in probably 10% of the time it took using SVN.
- There is no official UI for git, so you need to be somewhat familiar with the command line.
- Undoing a merge could be made easier, but there are definitely complications in allowing something like that.
September 29, 2017
The only version control system you really need.
We use Git for many varying purposes. The most obvious use case is for our code-based projects. Drupal modules, WordPress plugins, Composer packages, NPM modules, you name it--it's all in GitHub! Additionally, we use GitHub for managing libraries of shared code snippets, managing configuration files, holding Ansible playbooks, and the list goes on and on.
- Version control just about anything!
- Manage the code of projects both large and small
- Manage configuration
- Facilitate easy collaboration between developers
- Sometimes Git can be daunting to use, especially if you are new to it, and especially if you're on the command line.
- Many Git clients exist, but it would be great if Git had an official cross-platform desktop application. However, many alternative Git desktop applications exist.